Methods and Devices for Managing Connectivity for a Service

ABSTRACT

Methods, a wireless device ( 110 ) and a network node ( 120 ) for managing connectivity are disclosed. The wireless device ( 110 ) and/or the network node ( 120 ) determines an estimated level of a connectivity for a service of the wireless device ( 110 ) towards a wireless network ( 100 ). The estimated level of the connectivity relates to likelihood of maintaining the connectivity towards the wireless network ( 100 ). The estimated level of the connectivity is determined based on conditions relating to at least one connection for the wireless device ( 110 ). The at least one connection is managed by the wireless network ( 100 ). Moreover, corresponding computer programs and computer program products are disclosed.

TECHNICAL FIELD

Embodiments herein relate to wireless communication systems, such astelecommunication systems. A method and a wireless device for managingconnectivity for a service as well as a method and a network node formanaging connectivity for a service are disclosed. Moreover,corresponding computer programs and computer program products aredisclosed.

BACKGROUND

Today wireless communication systems are mainly used for human-centeredcommunication and services. A trend is, however, to use wirelesscommunication systems for communication and services mainly involvingmachines. This kind of communication and services are often referred toas Machine-to-Machine (M2M) communication.

Certain types of communication and services within M2M communication areexpected to require that a wireless connection, provided by the wirelesscommunication systems, is highly reliable. The wireless connection isrequired to be highly reliable both in terms of loss of the wirelessconnection and the possibility of establishing the wireless connection.In the following, the term “reliable” is used in this context.Therefore, for the above mentioned certain types of communication andservices within M2M communication, a high reliability of the connection,or the possibility to establish connection, may be said to be required.

This kind of high reliability may also be required for Person-to-Machine(P2M), Person-to-Person (P2P) and Machine-to-Person (M2P) communication.

Services that may need this kind of high reliability include industrialprocess control services, services for alarm monitoring, services insmart grid applications, control and management of business and/ormission critical processes or services, services for monitoring criticalinfrastructure and services towards responders in the national securityand public safety segment and other similar services.

Furthermore, high reliability for certain services may be beneficialwhere deployment of nodes, such as radio base station, radio networkcontroller etc., is particularly costly. At the same time, it is desiredto achieve sufficient capacity, e.g. in terms of number of connecteddevices, and/or coverage for the services.

Consider for example a device, such as smart meters for a smart grid, ametering, sensing or activation device, that is deployed in a network ata remote location at high cost. If there would be a failure incommunication with such a device e.g. due to bad coverage and/orinsufficient capacity, a manual restoration of the communication withthe device or a replacement of the device with another device would berequired to compensate for the failure. Such compensation may imply highlabor costs, which would scale in an unacceptable manner when there area great number of devices which often is the case in application of M2Mcommunication.

It is known to provide connectivity for M2M devices in a number ofdifferent ways using e.g. wired or wireless connections. The wiredconnections may be copper wires, optical fibers, Ethernet cables or thelike. The wireless connections may be provided by use of various RadioAccess Technologies (RATs), such as Wi-Fi, Evolved Universal TerrestrialRadio Access Network for Long Term Evolution (EUTRAN/LTE), UniversalTerrestrial Radio Access Network for High Speed Packet Access(UTRAN/HSPA), Global System for Mobile communication (GSM) for EnhancedData GSM Environment (EDGE) Radio Access Network (GERAN) and the like.Moreover, evolutions of the aforementioned RATs as well as other ThirdGeneration Partnership Project (3GPP) networks may be used to providethe wireless connection.

During planning of the radio access networks and/or telecommunicationsystems mentioned above, it is sometimes desired to set up the radioaccess network such as to provide a high reliability for M2M devices.High connectivity could then be provided in the following ways.

For example, the radio access network could be deployed asover-dimensioned in terms of transport and/or radio link resources.Over-dimensioning of transport resources may refer to use of opticalfibers for communication from a base station, while a peak bit-rate fromthe base station is 800 Megabits per second and an optical fiber mayhandle tenth of Gigabits per second. Over-dimensioning of radio linkresources refers to deployment of more base stations, antennas, use ofmore frequency bands, etc. than needed according to an estimated networkload. The RAN is said to be over-dimensioned when it is deployed to beable to handle a worst case scenario while still having resources thatare available for any upcoming communication.

A disadvantage with over-dimensioning of the radio access network isthat the transport and/or radio link resources may consume power and/orbecome occupied when made available in order to provide highconnectivity. Thus, the radio access network is operated inefficiently.Furthermore, over-dimensioning may be costly since number of sites, e.g.base stations, will be higher than if the system would be dimensionedonly for common, e.g. statistically common, loads of the system.

As another example, so called node availability may be increased byintroducing redundancy in a node by installing multiple power units forpowering of the node. The node availability may relate to availabilityof e.g. transport nodes, radio nodes and server nodes, which communicatewith the M2M device or control or support the network operation. Nodeavailability decreases on failure of a node, which typically happenswhen power units for powering of the node breaks down.

Again, a disadvantage may be that the nodes, such as transport nodes,radio nodes and server nodes, are operated inefficiently, since theredundancy is in most case not exploited.

SUMMARY

An object may be to enable improved operation in view of a missionand/or business critical service, which e.g. requires high reliabilityas mentioned above. In this context, improved operation may refer toincreased reliability of the operation of the mission critical serviceor the like.

According to a first aspect, the object is achieved by a method,performed by a wireless device, for managing connectivity. The wirelessdevice determines an estimated level of a connectivity for a service ofthe wireless device towards a wireless network. The estimated level ofthe connectivity relates to likelihood of maintaining the connectivitytowards the wireless network. The estimated level of the connectivity isdetermined based on conditions relating to at least one connection forthe wireless device. The at least one connection is managed by thewireless network.

According to a second aspect, the object is achieved by a wirelessdevice configured to manage connectivity. The wireless device isconfigured to determine an estimated level of a connectivity for aservice of the wireless device towards a wireless network. The estimatedlevel of the connectivity relates to likelihood of maintaining theconnectivity towards the wireless network. The estimated level of theconnectivity is determined based on conditions relating to at least oneconnection for the wireless device. The at least one connection ismanaged by the wireless network.

According to a third aspect, the object is achieved by a computerprogram for managing connectivity for a service. The computer programcomprises computer readable code units which when executed on a wirelessdevice causes the wireless device to perform the method describedherein.

According to a fourth aspect, the object is achieved by a computerprogram product, comprising a computer readable medium and a computerprogram as described directly above stored on the computer readablemedium.

According to a fifth aspect, the object is achieved by a method,performed by a network node, for managing connectivity. The network nodedetermines an estimated level of a connectivity for a service of awireless device towards the network node. The estimated level of theconnectivity relates to likelihood of maintaining the connectivitytowards the network node. The estimated level of the connectivity isdetermined based on conditions relating to at least one connection forthe wireless device. The at least one connection is managed by thenetwork node.

According to a sixth aspect, the object is achieved by a network nodeconfigured to manage connectivity. The network node is configured todetermine an estimated level of a connectivity for a service of awireless device towards the network node. The estimated level of theconnectivity relates to likelihood of maintaining the connectivitytowards the network node. The estimated level of the connectivity isdetermined based on conditions relating to at least one connection forthe wireless device. The at least one connection is managed by thenetwork node.

According to a seventh aspect, the object is achieved by a computerprogram for managing connectivity for a service, wherein the computerprogram comprises computer readable code units which when executed on anetwork node causes the network node to perform the method as describedherein.

According to an eighth aspect, the object is achieved by a computerprogram product, comprising a computer readable medium and a computerprogram as described directly above stored on the computer readablemedium.

With the embodiments herein, functionality in the wireless device or thenetwork node for determining, e.g. estimating, predicting and the like,the estimated level of connectivity for the service of the wirelessdevice is provided. Hence, the estimated level of the connectivity forthe service of the wireless device is determined based on at least oneconnection for the wireless device. The at least one connection for thewireless device may include existing connections as well as potentialconnections. Potential connections may refer to that it is predictedthat if the service would request a connection, the request would begranted. By use of the estimated level of the connectivity, the wirelessdevice and/or the network node is able to more efficiently adaptoperation to the estimated level of connectivity, which e.g. depends oncurrent network conditions, such as coverage, traffic load and the like.

An advantage may be that critical services may be implemented in awireless network while maintaining control of potential errors. Anadvantage of having knowledge about the estimated level of connectivityis that it enables critical services to be more efficiently monitoredand/or managed, e.g. adapted to conditions in the wireless network.

BRIEF DESCRIPTION OF THE DRAWINGS

The various aspects of embodiments disclosed herein, includingparticular features and advantages thereof, will be readily understoodfrom the following detailed description and the accompanying drawings,in which:

FIG. 1 is a schematic overview of an exemplifying wireless network inwhich embodiments herein may be implemented,

FIG. 2 is a block diagram illustrating states relating to level ofconnectivity,

FIG. 3 is another block diagram illustrating states relating to level ofconnectivity,

FIG. 4 is a schematic, combined signaling scheme and flowchartillustrating embodiments of the methods,

FIG. 5 is a block diagram illustrating embodiments of the wirelessdevice, and

FIG. 6 is a block diagram illustrating embodiments of the network node.

DETAILED DESCRIPTION

Throughout the following description similar reference numerals havebeen used to denote similar elements, units, modules, circuits, nodes,parts, items or features, when applicable. In the Figures, features thatappear in some embodiments are indicated by dashed lines.

FIG. 1 depicts an exemplifying wireless network 100 in which embodimentsherein may be implemented. In this example, the wireless network 100 isa Long Term Evolution (LTE) system. In other examples, the wirelessnetwork may be any cellular or wireless communication system, such as aWideband Code Division Multiple Access (WCDMA) network, a Global Systemfor Mobile communication (GSM network), Wireless Fidelity (Wi-Fi) or thelike.

Furthermore, a wireless device 110 and a network node 120 are shown inFIG. 1. The wireless network 100 may serve the wireless device 110. Insome examples, the network node 120 serves the wireless device 110. Thewireless device 110 and the network node 120 are capable ofcommunicating 150 with each other at least partly over the wirelessnetwork 100. In some examples, the network node 120 may be a radionetwork node 130.

As used herein, the terms “network node” or “radio network node” mayrefer to an evolved Node B (eNB), a control node controlling one or moreRemote Radio Units (RRUs), a radio base station, an access point, a userequipment, a car with radio/wireless communication capabilities, awireless machine-to-machine device or the like.

As used herein, the term “wireless device” may refer to a userequipment, a M2M device, a mobile phone, a cellular phone, a PersonalDigital Assistant (PDA) equipped with radio communication capabilities,a smartphone, a laptop or personal computer (PC) equipped with aninternal or external mobile broadband modem, a tablet PC with radiocommunication capabilities, a portable electronic radio communicationdevice, a sensor device equipped with radio communication capabilitiesor the like. The sensor may be any kind of weather sensor, such as wind,temperature, air pressure, humidity etc. As further examples, the sensormay be a light sensor, an electronic switch, a microphone, aloudspeaker, a camera sensor etc. The term “user” may indirectly referto the wireless device.

Before the embodiments herein are described, level of connectivity, as aconcept, is explained with reference to the block diagrams in FIG. 2 andFIG. 3. The wireless device 110 may be referred to as a M2M device 110.

Level of connectivity may also be referred to as connectivityavailability. Generally, the level of connectivity is herein defined asa probabilistically guaranteed promise that some sufficiently goodconnectivity, which e.g. fulfils service requirements for a specific M2Mservice, can be provided at or above some degree of likelihood. Servicerequirements are further described in section “service requirements”below. In some examples, the level of connectivity may be a valuerelating to likelihood of maintaining the connectivity towards thewireless network 100, such as the network node 120, for a service, suchas the specific M2M service or the like.

FIG. 2 shows a block diagram illustrating three exemplifying statesrelating to levels of connectivity. The three exemplifying statesincludes a first state 201 with no connectivity, a second state 202 withbasic level of connectivity and a third state 203 with high level ofconnectivity.

In this example, a level of connectivity is given by a probability valuebetween 0 and 1. Therefore, the level of connectivity may be a digit, avalue, a string of bits or the like, which is representing some specificlevel of connectivity. Thus, the level of connectivity relates tolikelihood, or probability, for a service, executed in the wirelessdevice 110, to maintain connectivity to the wireless network 100 and/ore.g. the network node 120.

To maintain the connectivity means that the wireless device 110 maymaintain, i.e. not drop, a wireless connection that has beenestablished.

Moreover, to maintain the connectivity means that the wireless device110 may establish, or set up, a wireless connection successfully withlikelihood given by the probability value. Since the connectivityapplies to the service, expressed herein as connectivity for theservice, service requirements for the service are accordingly fulfilledby the connectivity, e.g. the wireless connection, be it an alreadyexiting connection or a connection to be set up.

With the concept of level of connectivity, a required level of theconnectivity shall be distinguished from an estimated level of theconnectivity.

The required level of the connectivity may be determined by the service,i.e. the service, or in fact a person providing or handling the service,may set the required level of the connectivity to a certain values, e.g.0.9. For this reason, the required level of the connectivity may bereferred to as a desired, or even required, level of the connectivity.As mentioned above, level of connectivity in general may be representedby values between 0 and 1. Thus, a value of 0.9 may be considered torepresent a high level of connectivity. The required level of theconnectivity may also be a default level of the connectivity. Thedefault level of the connectivity may apply for a particular service ora group of services. In other examples, the required level of theconnectivity may be represented by descriptors as “poor”, “medium”,“high” or the like, which descriptors in turn may be associated withcertain ranges of the level of the connectivity.

The required level of the connectivity may, additionally oralternatively, be set by a network node, comprised in the wirelessnetwork 100. The network node may handle requests for services and/orconnections therefore. As an example, the network node may be an eNB inLTE, a Radio Network Controller (RNC), Mobility Management Entity (MME),Serving General Packet Radio Service Support Node (SGSN), Policy andCharging Rules Function (PCRF), Home Subscriber Server (HSS), HomeLocation Register (HLR) or the like. When the network node sets therequired level of the connectivity, it may set different levels of theconnectivity for different services, different users, i.e. differentnodes such as the wireless device 110 and the network node 120,different user groups, different types of devices and the like. Thedifferent users, or user groups, may be different in terms ofsubscriptions, home network etc. The different types of devices may bedifferent in terms of being mobile or stationary, a user device or amachine device and the like.

The estimated level of the connectivity may for example be determined asdescribed in section “Determining level of connectivity”. The estimatedlevel of the connectivity depends on radio conditions, traffic load etc.in the wireless network 100. Therefore, the estimated level of theconnectivity reflects actual, or real, level of the connectivity for theservice towards the wireless network. The estimated level may thuscorrespond to an actual, or current, level of the connectivity. As aconsequence, when the estimated level is increased, or decreased, itmeans that the actual level of the connectivity, which the estimatedlevel is an estimate of, is in fact increased, or decreased. Theincrease or decrease of the estimated level may occur due to thatcertain actions, e.g. relating to ensuring of the required level of theconnectivity, as described herein are performed.

As described above, the level of the connectivity may be expressed asprobability for a service to maintain connectivity to the wirelessnetwork 100. This means that the probability may be linked to a timeperiod. Hence, as an example, the probability of losing the connectivityduring an upcoming (future) time period is 0.9. In other examples, theprobability may relate to that an event occurs. The event may e.g. bethat a fire alarm report is in fact received by a probability of 0.9999which would set a requirement that there is connectivity when the firealarm actually goes off.

Furthermore, the level of the connectivity may be expressed as Mean TimeBetween Failures (MTBF). For example, when the MTBF of the connectivityis 100 years, failure is very rare.

The three exemplifying states relating to levels of the connectivity maybe seen as a quantization of the levels of the connectivity.

In FIG. 2, threshold values X and Y for deciding when to consider theservice to be in any one of the three states 201, 202, 203 relating tolevels of the connectivity are indicated. Expressed differently, anexemplifying M2M device (not shown) may be in one of the three statesdepending on relations between an estimated probability value relatingto the level of the connectivity and the threshold values X and Y. TheM2M device may be an example of the wireless device 110 and/or thenetwork node 120.

The estimated probability value may be given, e.g. indirectly ordirectly, by the estimated level of the connectivity. Hence, theestimated probability value may be given indirectly by the estimatedlevel of the connectivity when the estimated level of the connectivityrepresents a probability. For example, when the estimated level of theconnectivity is equal to 300, it represents e.g. a probability of 0.7.This means that the estimated level of the connectivity may need to betranslated, interpreted or the like, before it can be used as aprobability value. Alternatively, the estimated probability value may begiven directly by the estimated level of the connectivity when theestimated level of the connectivity is e.g. equal to 0.7. In this case,the estimated level of the connectivity can be used directly without aneed for translation, interpretation or the like, since probabilityvalues range from zero to one.

The three states are in this example defined as follow, starting withthe third state 203 for ease of explanation. In order to find out inwhich state the service is the estimated probability value may bedetermined as mentioned above. Throughout this example, it is assumedthat the same service requirements for the service apply in all states.

High Connectivity State

The M2M device may be in a so called high connectivity state aka thethird state. The connectivity may be considered high if the estimatedprobability value, here denoted PX, is e.g. above a threshold X. Whileusing the reference numerals in the Figure, we have that PX>X.

Basic Connectivity State

The M2M device may be in a so called basic connectivity state aka thesecond state. While assuming in this example that the estimatedprobability value is PY, the connectivity may be considered to be basicif PY is e.g. above a threshold Y. At the same time, PY is not highenough to reach the high connectivity state, i.e. the estimatedprobability value PY is less than the threshold X. While using thereference numerals in the Figure, we have that Y<PY<X.

No Connectivity

The M2M device may be in a state of no connectivity aka the first state.In this state, the M2M device has no connection to the network or aconnection that does not fulfil the service requirements, and the M2Mdevice has therefore no service. Furthermore, the M2M device may nothave, as far as it can be estimated, any possibility to obtain aconnection. This means that the estimated probability value, now denotedby PZ, is not high enough to reach the basic connectivity state. As anexample, the M2M device may be out-of-coverage in view of the wirelessnetwork 100. While using the reference numerals in the Figure, we havethat PZ<Y.

In the description above, the M2M device is said to be in the differentstates mentioned above for reasons of simplicity. In some examples, incase a M2M device runs multiple services, each of those multipleservices may be said to be in the different states. Some or all of themultiple services may be in the same state or all of the multipleservices may be in a respective state.

In the following description, two example scenarios will be referred toin order to improve understanding.

In a first exemplifying scenario, the wireless network 100 is includedin, or forms a part of, a traffic control system, which includes variousentities, e.g. traffic lights, vehicle such as car and trucks,bicyclists carrying cellular phones. At least some of the entitiescommunicate over the wireless network 100. This means that some entitiesof the traffic control system may be within the wireless network 100 andsome other entities may be outside the wireless network 100.

As an example, some functions related to control of vehicles etc. can beautomated when the high connectivity state is reached or available, butthese functions need to operate in a half-automatic or manual mode forsafety reasons when only basic connectivity state is reached oravailable.

In a second exemplifying scenario, the wireless network 100 is includedin an industrial control system or power system. The industrial controlsystem may comprise various entities, such as valves, transportationbelts, spray devices for painting or physical/chemical treatment etc. Atleast some of the entities communicate over the wireless network 100.This means that some entities of the industrial control system may bewithin the wireless network 100 and some other entities may be outsidethe wireless network 100.

The industrial control system may operate at lower margins with higherefficiency, e.g. higher yield, when the entities communicating over thewireless network 100 have high connectivity state, e.g. with boundedlatency, compared to when the entities only have basic connectivitystate, which would require higher margins since the industrial controlsystem needs e.g. more time to react, treat, open/close valves etc.

In the second scenario, it may be that the industrial control system isoperated based on local information, or half-automatic mode, when theentities communication over the wireless network 100 have lowconnectivity state. Local information may have been stored in theentities prior to the low connectivity state.

In FIG. 3, another block diagram illustrates a more general case with Nnumber of states relating to level of connectivity. As illustrated inthis Figure, the states shown in FIG. 2 may be extended to includeadditional states with different levels of connectivity, e.g. withdifferent transition probabilities X1 . . . XN for transition from onestate to another.

FIG. 4 illustrates an exemplifying method for managing connectivity fora service when performed in connection with the wireless network 100 ofFIG. 1.

For simplicity the method performed by the wireless device 110 isdescribed separately from the method performed by the network node 120.

The following actions may be performed in any suitable order.

Action 401

The wireless device 110 determines an estimated level of a connectivityfor a service of the wireless device 110 towards a wireless network 100.The estimated level of the connectivity relates to likelihood ofmaintaining the connectivity towards the wireless network 100. Theestimated level of the connectivity is determined based on conditionsrelating to at least one connection for the wireless device 110. The atleast one connection is managed by the wireless network 100.

The conditions relating to said at least one connection may include atleast one of:

-   -   number of connections for the wireless device 110;    -   quality of connections for the wireless device 110;    -   variance of quality of connections for the wireless device 110;    -   correlation between connections for the wireless device 110;    -   network conditions impacting connections for the wireless device        110 and the like.

For each of the conditions, it will be described how the estimated levelof the connectivity may be determined in section “Determining level ofconnectivity” below.

The determined estimated level of the connectivity relates totransmission to/from the wireless network 100. That is to say, theestimated level of connectivity may include two values, one for uplink,i.e. transmission from the wireless device 110, and one for downlink,i.e. transmission to the wireless device 110.

Action 402

The wireless device 110 may send, to a network node 120, a message forenabling the network node 120 to adapt its operation based on theestimated level of the connectivity.

The message may comprise, e.g. represent, the estimated level of theconnectivity.

The message may indicate, in a binary manner, whether or not theestimated level of the connectivity exceeds a required level of theconnectivity for the service. As an example, the message may indicate‘1’ for when the estimated level exceeds the required level and ‘0’ forwhen the estimated level is below the required level.

The message may indicate the conditions relating to said at least oneconnection.

Action 404

The wireless device 110 may adapt its operation based on the estimatedlevel of the connectivity. Reference is made to section “adaptingoperation” below.

Now the actions performed by the network node 120, which also performs amethod for managing connectivity, will be described. As mentioned forthe wireless device 110, the following actions may be performed by thenetwork node 120 in any suitable order

Action 405

The network node 120 determines an estimated level of the connectivityfor a service of a wireless device 110 towards the network node 120. Theestimated level of the connectivity relates to likelihood of maintainingthe connectivity towards the network node 120. The estimated level ofthe connectivity is determined based on conditions relating to at leastone connection for the wireless device 110. The at least one connectionis managed by the network node 120.

The conditions relating to said at least one connection may include atleast one of:

number of connections for the wireless device 110;

quality of connections for the wireless device 110;

variance of quality of connections for the wireless device 110;

correlation between connections for the wireless device 110;

network conditions impacting connections for the wireless device 110.

Action 407

The network node 120 may send, to the wireless device 110, a message forenabling the wireless device 110 to adapt its operation based on theestimated level of the connectivity. The message may comprise theestimated level of the connectivity.

The message may indicate, in a binary manner, whether or not theestimated level of the connectivity exceeds a required level of theconnectivity for the service.

The message may indicate the conditions relating to said at least oneconnection.

Action 408

The network node 120 may adapt its operation based on the estimatedlevel of the connectivity. Reference is made to section “adaptingoperation” below.

The actions 405-408 performed by the network node 120 are similar toactions 401-404 performed by the wireless device 110. Therefore, ageneralized method performed by a wireless node, such as the wirelessdevice 110 or the network node 120, may include a first action includingaction 401 and 405, a second action including action 402 and 406, athird action including action 403 and 407 and a fourth action includingaction 404 and 408, where the first, second, third and fourth actionsare performed by the wireless node.

Action 402 and 407 may be performed at service start. Additionally,these actions may be performed when the estimated level of connectivitychanges, i.e. action 401 and/or 406 is/are performed multiple times anda difference between the determined consecutive estimated levels ofconnectivity represents a change. In case, the change between twodetermined consecutive estimated levels is greater than a threshold forwhen to take the change into account. Thus, this merely means that toosmall, e.g. with regard to the threshold, changes will be disregarded.

Determining Level of Connectivity

As mentioned, the wireless network 100 may determine the level of theconnectivity based on one or more conditions relating to at least oneconnection for the wireless device 110, the network node 120 and/or theservice. In the following the term “M2M device” will be used to refer tothe wireless device 110, the network node 120 and/or the service.

The expression “a connection for the M2M device” refers to that aconnection is usable by the M2M device.

The connection that is useable by the wireless device 110 shall beunderstood to mean a connection which the M2M device is capable of usingor which the M2M device already uses. The connection that the M2M deviceis capable of using may be called a potential or possible connection.Thus, the potential connection for the M2M device is not yetestablished, i.e. the M2M device is not attached to the wireless network100 by means of such potential connection.

An already used connection does not necessarily mean that the connectionis actively used for transmission of data. Instead, it is enough thatthe already used connection is established between the wireless device110 and e.g. the second node 120. For LTE, this means that the wirelessdevice 110 can be in either so called idle mode or connected mode, whichmodes are referred to as RRC_IDLE and RRC_CONNECTED in TechnicalSpecification (TS) 36.331 of the 3GPP group.

In the following examples, criteria for when to consider the level ofconnectivity to be high are given.

As a first example, the conditions relating to the at least oneconnection for the M2M device include, as mentioned, the number ofconnections for the M2M device.

At least U number of possible connections, which sometimes may be calledconnectivity links or paths, may be provided to the M2M device at asufficiently good link quality.

Possible connections may be:

-   -   connections of the same radio technology, e.g. same or different        frequency carriers, but e.g. to different base stations,    -   connections of the same radio technology to the same base        stations but at different frequencies,    -   connections provided via different radio technologies, e.g. to        the same or different base stations,    -   connections that provide connectivity to different access        networks/operators,    -   fixed/wired connections, such as copper wires and the like.

Base station may here refer to radio network nodes, access points, relaynodes, repeaters and the like.

For the case above, the different connections can either be establishedsimultaneously to the device or in case only some of the connections areestablished it is predicted, based e.g. on measurements, that it wouldbe possible to establish the alternative connections in case the firstset of connections are deemed lost.

As a second example, the conditions relating to the at least oneconnection for the M2M device include, as mentioned, the quality ofconnections for the M2M device.

The connections of the M2M device may be provided at a desired QoS levelwith a significant so called link margin.

For example, when the required transmit power of the M2M device isconsistently X dB below the permitted power as determined by thewireless network 100 e.g. depending on interference restrictions.

As other example, the required radio resources for a connection areconsistently Y % less than what is allocated, or available, for aconnection. In detail, this may be that only half, i.e. Y=50%, of thebit rate specified for the connection, i.e. a Guaranteed Bit Rate (GBR)bearer, is used.

As a third example, the conditions relating to the at least oneconnection for the M2M device include, as mentioned, the variance ofquality of connections for the M2M device. When the variance of qualityof connections is below Z for all or at least S number of connections,then the level of connectivity may be considered high, assuming theaverage quality of the connections is considered good as is explained inthe example below.

An example of quality of connections is connection margin, or linkmargin. Now assume that the M2M device has a certain level ofconnectivity, e.g. there are two connections available with at least 10dB margin beyond what is needed for the required quality of service. Thecertain level of connectivity may be considered as a fulfilling the highconnectivity state requirement if the margin has been stable over a timeperiod. E.g. the margin was at least 10 dB during 95% of the time duringthe last 180 days, and variance of the margin was below a threshold Z.

At the same time, another M2M device with the same certain level ofconnectivity may be considered as not fulfilling the high connectivitystate requirement for this other M2M device. As reason for this may bethat in order to consider the other M2M device to fulfill the highconnectivity state requirement, it may be required that the margin isvery stable, i.e. variance of the margin should be less than P, whereP=0.7*Z as an example. This means that P<Z.

In these manners, the estimated level of the connectivity for the M2Mdevice is taking time dynamics of the quality of connections intoaccount.

As a fourth example, the conditions relating to the at least oneconnection for the M2M device include, as mentioned, the correlationbetween connections for the M2M device. When the correlation ofconnections is below U for all or at least T number of connections, thenthe level of connectivity may be considered high.

As an example, connections which have many common elements or propertiesare considered to have high correlation, while connections which havedifferent elements or properties have low correlation. Examples ofelements include nodes, transport links, antennas, hardwareconfiguration and the like. Examples of properties include radiofrequency band, radio access technology or the like.

As a further example, assume a first path has a set of nodes x1 andlinks y1 and networks z1 to pass through, and a second path hasaccordingly x2/y2/z2 nodes/links/networks. A failure correlation, e.g.given as a value between 0 for no correlation and 1 for full correlationis determined e.g. by the M2M device. This can e.g. be done bydetermining how many of the x1/y1/z1 are common with x2/y2/z2. In thiscorrelation also characteristics of the different elements in x/y/z maybe considered. E.g. if the first and second paths share a commonbackhaul link, this link is determined to affect the correlationlargely; at the same time, if the first and second paths share a commonoptical fiber transport link between two cities, this transport link maybe considered as not affecting the correlation strongly, if it isdetermined that this link has a low probability of failure or atechnical fallback mechanism in-build. Essentially this means thatdifferent nodes and links are assigned different weights depending onthe individual reliability of the node and link when determining theoverall failure correlation.

As a fifth example, the conditions relating to the at least oneconnection for the M2M device include, as mentioned, the networkconditions impacting connections for the M2M device. The networkconditions may be network load, radio interference, radio obstructionsetc. The network load may refer to traffic generated from other users ina local area of the M2M device, number of active users etc. The radiointerference may relate to harmful radio transmission received fromother users, which decreases signal quality received at the M2M device.The radio obstructions may be if a user is in or behind a house whichleads to weaker radio signals.

In further examples, the conditions relating to the at least oneconnection for the M2M device may include information about themobility, e.g. stationary, limited movement, fully mobile, andcapabilities of the M2M device, e.g. supported radio access, supportedfrequency bands, processing capabilities, power classes, etc.

Adapting Operation

Now that the M2M device has received or estimated the estimated level ofconnectivity, the M2M device is able to adapt its operation based on theestimated level of connectivity. As mentioned before, the wirelessdevice 110 and/or the network node 120 may be referred to as the M2Mdevice.

One way of adapting the operation for the M2M device is to select a modeof operation for the service, referred to as service mode, based on theestimated level of the connectivity.

The M2M device selects one of the service modes based on the level ofthe connectivity. As an example, the M2M device may select a servicemode that is proportional to the level of the connectivity when theservice mode is represented by a number, or digit. Higher numbers maycorrespond to that higher levels of the connectivity are required forthe service to be executed with high reliability, e.g. in a securemanner or fail safe manner. A high level of the connectivity typicallymeans that there is a high probability, e.g. above a threshold valuesuch as 0.9, that the connectivity will be maintained.

In some embodiments, the service modes may comprise at least two modesof operation. Thus, the service modes may comprise a first service modeand a second service mode.

In these embodiments, the M2M device may select the first service modewhen the estimated level of the connectivity exceeds a first value ofconnectivity for allowing the service to be operated in the firstservice mode. The first value may be specified in a standard,pre-configured by end user/operator, and signaled dynamically e.g. whenthe M2M device registers to the wireless network 100. Alternatively, theM2M device may select the second service mode when the estimated levelof the connectivity exceeds a second value of connectivity for allowingthe service to be operated in the second service mode.

As an example, a control system may comprise the M2M device and acontroller node for controlling the M2M device. In this example, theservice of the M2M device may be said to be allowed to be operated inthe first or second service mode when the control system is stable.Stable, or stability, has its conventional meaning when used inconnection automatic control engineering, i.e. the control system maynot easily be set into a state where control signals oscillate or areoutdated such that the control system ceases to work as intended.

Another way of adapting the operation for the M2M device is to adjust anamount of probe messages based on the required level of the connectivityand the estimated level of the connectivity. Thanks to sending of probemessages the M2M device may determine if it has connectivity, e.g. byreceiving a response to the sent probe message.

In case, the M2M device is a so called device server, it may send probemessages to determine if it has lost connectivity to a client devicebecause the device server does no longer receive the probe messages sentby the client device, i.e. the probe messages are sent from the clientdevice as keep alive signaling. In this context, a device server isserving the client device with respect to a service executed by theclient device.

The probe messages are sent, by the M2M device, to the wireless network100 for verification of the required level of the connectivity.

The amount of the probe messages may relate to one or more of:

a periodicity at which the probe messages are sent from the M2M device;

number of cells to which the probe messages are sent;

number of radio access technologies used when the probe messages aresent;

number of carriers used when the probe messages are sent, and the like.

The periodicity at which the probe messages are sent from the M2M devicemay be an indication of in which time slots, the M2M device may send theprobe messages. The periodicity may sometime be given by a frequencyvalue.

The number of cells, typically per each radio access technology used, towhich the probe messages are sent may relate to a number of radionetwork nodes, such as the radio network node 130, to which the probemessages are sent or broadcast.

The number of radio access technologies used when the probe message aresent may be that one radio network node, such as the radio network node130, is a multi-RAT radio network node. Then, it may be that the probemessages are sent on connections using some or all of these multi-RATsin order to adjust the amount of probe messages sent.

The number of carriers, or carrier frequencies, used when the probemessages are sent may be that one radio network node, such as the radionetwork node 130, is capable of transmitting and receiving at aplurality of frequencies. Then, it may be that the probe messages aresent on connections using some or all of the plurality of frequencies inorder to adjust the amount of probe messages sent.

As already mentioned above, the amount of probe message may relate to acombination of one or more of the above mentioned meanings of the amountof probe messages. Hence, the adjusting of the amount of the probemessages may be an adaption of number of the probe messages sent overvarious connections, or links, according to the above.

A further way of adapting operation may be that the network node 120adapts operation by configuring a first set of resources to increase anestimated level of the connectivity for the service. Hence, the networknode 120 ensures, or attempts to ensure, that the required level ofconnectivity is fulfilled.

Hence, the first network node 120 may configure the first set ofresources according to one or more of the following manners. In theparagraphs below, the network node 120 will be referred to as “ensuringnode”.

In a first manner, the ensuring node may configure the first set ofresources by reserving a sub-set of the first set of resources for theservice, wherein at least the sub-set of resources are required toensure the required level of the connectivity.

As an example, the first set of resources may be resources blocks, suchas Physical Resource Blocks, of a time-frequency grid in LTE. Then, theensuring node may reserve a sub-set of the resource blocks such thatthese resources blocks are available for the service when required.

As an example, the reserved sub-set of the first set of resources may bereserved by that if a request for service of the same or less Allocationand Retention Policy (ARP) priority is received at the ensuring node,the ensuring node may need to reject such request for service if thereserved sub-set of resources would be allocated when admitting therequest.

In a second manner, the ensuring node may configure the first set ofresources by reducing an amount of the first set of resources, whichamount of the first set of resources are assigned to a further servicein advance of or when the service becomes active.

As mentioned, the first set of resources may be resources blocks, suchas Physical Resource Blocks, of a time-frequency grid in LTE. Then, theensuring node may determine that a specific amount of resources blocksare used by the further service. Thereafter, the ensuring node mayreduce the specific amount such that the service is prioritized at theexpense of the further service, which may degrade, such as experiencedelays, or even interruption.

In a third manner, the ensuring node may configure the first set ofresources by moving a further service, to which some of the first set ofresources have been assigned, in advance of or when the service becomesactive, to a second set of resources. The second set of resources isdifferent from the first set of resources.

As an example, the ensuring node may perform a handover or a cell changeorder to move at least one further wireless device to another cell,another frequency band or another Radio Access Technology (RAT) thanthat of the wireless device 120. The cell change order may mean that theensuring node sends a message for instructing the further wirelessdevice to perform a change cell, or perform cell reselection.

In a fourth manner, the ensuring node may configure the first set ofresources by increasing the first set of resources by allocating furtherRandom Access (RA) channels to the service and/or transmit withincreased transmit power.

As an example relating to the allocation of further RA channels, theensuring node may configure different number of occasions in time, e.g.periodicity in terms of 5 ms, 10 ms or the like, and different number ofoccasions in frequency, e.g. in terms of 1, 2, 3 Resource Blocks (RB) orthe like. It may here be noted that the number of Random Accessoccasions, i.e. in terms of time and/or frequency, are configured percell in LTE. With many occasions, i.e. many RA resources/channels, itmeans that the total number of uplink RBs that can be used for data willbe fewer, but the success rate of the Random Access Channel will behigher even at high network load. Thus, the level of the connectivitymay be ensured e.g. in terms of being fulfilled, or the level of theconnectivity may at least be increased.

As an example relating to transmit with higher power, the ensuring nodemay increase transmit power for the user whose level of connectivity isto be ensured. This may lead to that the ensuring node reduces transmitpower assigned to other users, i.e. those users for which level ofconnectivity is not to be ensured.

In yet further examples, a more robust coding may be used for the userswhose level of connectivity is to be ensured, or increased.

In a fifth manner, the ensuring node may configure the first set ofresources by setting up a connection towards the wireless device 110while using at least some of the first set of resources.

In an example, it is assumed that a user for which the level of theconnectivity is to be ensured, or increased, has a first connectionwhich uses a first radio access technology. Then the ensuring node mayset up a further connection which uses a second radio access technology,which is different from the first radio access technology. This may bebeneficial for the user if the user is considered to have highconnectivity when there are at least two existing connections.

In a sixth manner, the ensuring node may configure the first set ofresources by sending a message to the wireless device 110. The messageinstructs the wireless device 110 to measure on non-serving cells,non-serving frequencies, non-serving Radio Access Technologies to find athird set of resources for increasing the estimated level of theconnectivity. The third set of resources is different from the first setof resources.

As mentioned above, the ensuring node may combine one or more of thefirst to sixth manners to obtain yet further manners of configuring thefirst set of resources.

In some further embodiments relating to how the level of theconnectivity is determined and/or ensured, selected roaming may be takeninto account. Selected roaming refers herein to that the wireless deviceis configured to roam into another network on request by a so calledhome network, not due to out of coverage of the home network. Hence,selected roaming may be enabled for the wireless device in order todetermine the estimated level of the connectivity or in order to ensure,or attempt to ensure, the required level of the connectivity.

Note that enabling the wireless device for selected roaming may implyadditional costs for an operator, depending on existing roamingagreements. E.g. an operator may limit number of wireless devices forwhich selected roaming is possible, or the cost of the roaming agreementdepend on number of wireless devices that make use (or are configuredfor) selected roaming, or the amount of roaming traffic. For thisreason, the operator may try to limit number of wireless devices thatmake use of selected roaming to be as few as possible. At the same time,new devices/services may require connectivity availability that may notalways be provided by the operator. Since the wireless device isexpected to provide relatively high revenue for the operator there is adesire to be able to fulfill the connectivity requirements, e.g. givenby the required level of the connectivity. This may be done via selectedroaming.

The selected roaming may be configured per type of wireless device, e.g.devices that require a high required level of the connectivity.

The selected roaming may be configured per service request, e.g.services that require a high required level of connectivity.

The selected roaming may be configured only if a required level ofconnectivity is possible to be achieved at a specific time or location.E.g. the estimated level of the connectivity is determined, and if athreshold is not met selected roaming is enabled for the wirelessdevice.

The selected roaming is enabled by providing a re-configuration of themobile device (e.g. via device management) to re-configure the list ofenabled PLMN networks.

It may also comprise a configuration message to an administration serverin the partnering network to add a specific device to the list ofenabled devices for roaming (or increase the number of devices of thefirst operator that may make use of roaming). This has the purpose thatthe device is not rejected from establishing connectivity when itregisters in the other target network.

These embodiments may increase the estimated level of connectivity ormay aid in ensuring a required level of the connectivity in acost-effective form by enabling on-demand roaming amongoperators/networks.

Service Requirements

In a wireless communication system like LTE, the service requirementsmay be defined by a set of parameters relating to Quality of Service(QoS). In 3GPP Technical Specification (TS) 23.203, a set of QoS ClassIndicators (QCI) are described. The service that is set up is thusassociated with a certain QCI, in e.g. a range from 1 to 9. Each QCIdescribes for example acceptable delay and error rate for the associatedservice.

Service requirements are also defined for GSM, UTRAN and the like.

With reference to FIG. 5, a schematic block diagram of the wirelessdevice 110 is shown. The wireless device 110 is configured to performthe methods in FIG. 4. Thus, the wireless device 110 is configured tomanage connectivity

According to some embodiments herein, the wireless device 110 maycomprise a processing module 510. In further embodiments, the processingmodule 510 may comprise one or more of a determining module 520, asending module 530, and an adapting module 540 as described below.

The wireless device 110, the processing module 510 and/or thedetermining module 520 is configured to determine an estimated level ofa connectivity for a service of the wireless device 110 towards awireless network 100. The estimated level of the connectivity relates tolikelihood of maintaining the connectivity towards the wireless network100. The estimated level of the connectivity is determined based onconditions relating to at least one connection for the wireless device110. The at least one connection is managed by the wireless network 100.

-   -   The conditions relating to said at least one connection may        include at least one of:    -   number of connections for the wireless device 110;    -   quality of connections for the wireless device 110;    -   variance of quality of connections for the wireless device 110;    -   correlation between connections for the wireless device 110;    -   network conditions impacting connections for the wireless device        110.

The wireless device 110, the processing module 510 and/or the sendingmodule 520 may be configured to send, to a network node 120, a messagefor enabling the network node 120 to adapt operation based on theestimated level of the connectivity. The operation to be adapted mayrefer to operation of the network node 120. The message may comprise theestimated level of the connectivity.

The message may indicate, in a binary manner, whether or not theestimated level of the connectivity exceeds a required level of theconnectivity for the service.

The message may indicate the conditions relating to said at least oneconnection.

The wireless device 110, the processing module 510 and/or the adaptingmodule 540 may be configured to adapt operation based on the estimatedlevel of the connectivity. The adapted operation may refer to operationof the wireless device 110.

The wireless device 110 may further comprise an Input/output (I/O) unit504 configured to send and/or receive the message, the estimated levelof the connectivity and other messages, values, indications and the likeas described herein. The I/O unit 504 may comprise the sending module520, a transmitter and/or a receiver.

Furthermore, the wireless device 110 may comprise a memory 505 forstoring software to be executed by, for example, the processing modulewhen the processing module is implemented as a hardware modulecomprising at least one processor or the like.

FIG. 5 also illustrates software in the form of a computer program 501for managing connectivity for a service. The computer program 501comprises computer readable code units which when executed on thewireless device 110 causes the wireless device 110 to perform the methodaccording to FIG. 4.

Finally, FIG. 5 illustrates a computer program product 502, comprisingcomputer readable medium 503 and the computer program 501 as describeddirectly above stored on the computer readable medium 503.

With reference to FIG. 6, a schematic block diagram of the network node120 is shown. The network node 120 is configured to perform the methodsin FIG. 4. Thus, the network node 120 is configured to manageconnectivity.

According to some embodiments herein, the network node 120 may comprisea processing module 610. In further embodiments, the processing module610 may comprise one or more of a determining module 620, a sendingmodule 630, and an adapting module 640 as described below.

The network node 120, the processing module 610 and/or the determiningmodule 620 is configured to determine an estimated level of aconnectivity for a service of a wireless device 110 towards the networknode 120. The estimated level of the connectivity relates to likelihoodof maintaining the connectivity towards the network node 120. Theestimated level of the connectivity is determined based on conditionsrelating to at least one connection for the wireless device 110. The atleast one connection is managed by the network node 120.

-   -   The conditions relating to said at least one connection may        include at least one of:    -   number of connections for the wireless device 110;    -   quality of connections for the wireless device 110;    -   variance of quality of connections for the wireless device 110;    -   correlation between connections for the wireless device 110;    -   network conditions impacting connections for the wireless device        110.

The network node 120, the processing module 610 and/or the sendingmodule 630 may be configured to send, to the wireless device 110, amessage for enabling the wireless device 110 to adapt operation based onthe estimated level of the connectivity. The operation to be adapted mayrefer to operation of the wireless device 110. The message may comprisethe estimated level of the connectivity.

The message may indicate, in a binary manner, whether or not theestimated level of the connectivity exceeds a required level of theconnectivity for the service.

The message may indicate the conditions relating to said at least oneconnection.

The network node 120, the processing module 610 and/or the adaptingmodule 640 may be configured to adapt operation based on the estimatedlevel of the connectivity. The adapted operation may refer to operationof the network node 120.

The network node 120 may further comprise an Input/output (I/O) unit 604configured to send and/or receive the message, the estimated level ofthe connectivity and other messages, values, indications and the like asdescribed herein. The I/O unit 604 may comprise the sending module 620 atransmitter and/or a receiver.

Furthermore, the network node 120 may comprise a memory 605 for storingsoftware to be executed by, for example, the processing module when theprocessing module is implemented as a hardware module comprising atleast one processor or the like.

FIG. 6 also illustrates software in the form of a computer program 601for managing connectivity for a service. The computer program 601comprises computer readable code units which when executed on thenetwork node 120 causes the network node 120 to perform the methodaccording to FIG. 4.

Finally, FIG. 6 illustrates a computer program product 602, comprisingcomputer readable medium 603 and the computer program 601 as describeddirectly above stored on the computer readable medium 603.

As used herein, the term “resource” may refer to a certain coding of asignal and/or a time frame and/or a frequency range in which the signalis transmitted. In some examples, a resource may refer to one or morephysical resource blocks (PRB) which are used when transmitting thesignal. In more detail, a PRB may be in the form of orthogonal frequencydivision multiplexing (OFDM) PHY resource blocks (PRB). The term“physical resource block” is known from 3GPP terminology relating toe.g. Long Term Evolution Systems.

As used herein, the term “processing module” may refer to a processingcircuit, a processing unit, a processor, an Application Specificintegrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or thelike. As an example, a processor, an ASIC, an FPGA or the like maycomprise one or more processor kernels. In some examples, the processingmodule may be embodied by a software module or hardware module. Any suchmodule may be a determining means, estimating means, capturing means,associating means, comparing means, identification means, selectingmeans, receiving means, transmitting means or the like as disclosedherein. As an example, the expression “means” may be a module, such as adetermining module, selecting module, etc.

As used herein, the expression “configured to” may mean that aprocessing circuit is configured to, or adapted to, by means of softwareconfiguration and/or hardware configuration, perform one or more of theactions described herein.

As used herein, the term “memory” may refer to a hard disk, a magneticstorage medium, a portable computer diskette or disc, flash memory,random access memory (RAM) or the like. Furthermore, the term “memory”may refer to an internal register memory of a processor or the like.

As used herein, the term “computer readable medium” may be a UniversalSerial Bus (USB) memory, a DVD-disc, a Blu-ray disc, a software modulethat is received as a stream of data, a Flash memory, a hard drive, amemory card, such as a MemoryStick, a Multimedia Card (MMC), etc.

As used herein, the term “computer readable code units” may be text of acomputer program, parts of or an entire binary file representing acomputer program in a compiled format or anything there between.

As used herein, the terms “number”, “value” may be any kind of digit,such as binary, real, imaginary or rational number or the like.Moreover, “number”, “value” may be one or more characters, such as aletter or a string of letters. “number”, “value” may also be representedby a bit string.

As used herein, the expression “in some embodiments” has been used toindicate that the features of the embodiment described may be combinedwith any other embodiment disclosed herein.

Even though embodiments of the various aspects have been described, manydifferent alterations, modifications and the like thereof will becomeapparent for those skilled in the art. The described embodiments aretherefore not intended to limit the scope of the present disclosure.

1-28. (canceled)
 29. A method, performed by a wireless device, formanaging connectivity, wherein the method comprises: determining anestimated level of a connectivity for a service of the wireless devicetowards a wireless network, wherein the estimated level of theconnectivity relates to likelihood of maintaining the connectivitytowards the wireless network, wherein the estimated level of theconnectivity is determined based on conditions relating to at least oneconnection for the wireless device, wherein the at least one connectionis managed by the wireless network.
 30. The method of claim 29, whereinthe method comprises: sending, to a network node, a message for enablingthe network node to adapt operation based on the estimated level of theconnectivity, wherein the operation to be adapted refers to operation ofthe network node, wherein the message comprises the estimated level ofthe connectivity.
 31. The method of claim 29, wherein the methodcomprises: adapting operation based on the estimated level of theconnectivity, wherein the adapted operation refers to operation of thewireless device.
 32. The method of claim 29, wherein the conditionsrelating to said at least one connection include at least one of: anumber of connections for the wireless device; a quality of connectionsfor the wireless device; a variance of quality of connections for thewireless device; a correlation between connections for the wirelessdevice; network conditions impacting connections for the wirelessdevice.
 33. The method of claim 30, wherein the message indicates, in abinary manner, whether or not the estimated level of the connectivityexceeds a required level of the connectivity for the service.
 34. Themethod of claim 30, wherein the message indicates the conditionsrelating to said at least one connection.
 35. A method, performed by anetwork node, for managing connectivity, wherein the method comprises:determining an estimated level of a connectivity for a service of awireless device towards the network node, wherein the estimated level ofthe connectivity relates to likelihood of maintaining the connectivitytowards the network node, wherein the estimated level of theconnectivity is determined based on conditions relating to at least oneconnection for the wireless device, wherein the at least one connectionis managed by the network node.
 36. The method of claim 35, wherein themethod comprises: sending, to the wireless device, a message forenabling the wireless device to adapt operation based on the estimatedlevel of the connectivity, wherein the operation to be adapted refers tooperation of the wireless device, wherein the message comprises theestimated level of the connectivity.
 37. The method of claim 35, whereinthe method comprises: adapting operation based on the estimated level ofthe connectivity, wherein the adapted operation refers to operation ofthe network node.
 38. The method of claim 35, wherein the conditionsrelating to said at least one connection include at least one of: anumber of connections for the wireless device; a quality of connectionsfor the wireless device; a variance of quality of connections for thewireless device; a correlation between connections for the wirelessdevice; network conditions impacting connections for the wirelessdevice.
 39. The method of claim 36, wherein the message indicates, in abinary manner, whether or not the estimated level of the connectivityexceeds a required level of the connectivity for the service.
 40. Themethod of claim 36, wherein the message indicates the conditionsrelating to said at least one connection.
 41. A wireless deviceconfigured to manage connectivity, wherein the wireless device isconfigured to determine an estimated level of a connectivity for aservice of the wireless device towards a wireless network, wherein theestimated level of the connectivity relates to likelihood of maintainingthe connectivity towards the wireless network, wherein the estimatedlevel of the connectivity is determined based on conditions relating toat least one connection for the wireless device, wherein the at leastone connection is managed by the wireless network.
 42. The wirelessdevice of claim 41, wherein the wireless device is configured to send,to a network node, a message for enabling the network node to adaptoperation based on the estimated level of the connectivity, wherein theoperation to be adapted refers to operation of the network node, whereinthe message comprises the estimated level of the connectivity.
 43. Thewireless device of claim 41, wherein the wireless device is configuredto adapt operation based on the estimated level of the connectivity,wherein the adapted operation refers to operation of the wirelessdevice.
 44. The wireless device of claim 41, wherein the conditionsrelating to said at least one connection include at least one of: anumber of connections for the wireless device; a quality of connectionsfor the wireless device; a variance of quality of connections for thewireless device; a correlation between connections for the wirelessdevice; network conditions impacting connections for the wirelessdevice.
 45. The wireless device of claim 42, wherein the messageindicates, in a binary manner, whether or not the estimated level of theconnectivity exceeds a required level of the connectivity for theservice.
 46. The wireless device of claim 42, wherein the messageindicates the conditions relating to said at least one connection.
 47. Anetwork node configured to manage connectivity, wherein the network nodeis configured to determine an estimated level of a connectivity for aservice of a wireless device towards the network node, wherein theestimated level of the connectivity relates to likelihood of maintainingthe connectivity towards the network node, wherein the estimated levelof the connectivity is determined based on conditions relating to atleast one connection for the wireless device, wherein the at least oneconnection is managed by the network node.
 48. The network node of claim47, wherein the network node is configured to send, to the wirelessdevice, a message for enabling the wireless device to adapt operationbased on the estimated level of the connectivity, wherein the operationto be adapted refers to operation of the wireless device, wherein themessage comprises the estimated level of the connectivity.
 49. Thenetwork node of claim 47, wherein the network node is configured toadapt operation based on the estimated level of the connectivity,wherein the adapted operation refers to operation of the network node.50. The network node of claim 47, wherein the conditions relating tosaid at least one connection include at least one of: a number ofconnections for the wireless device; a quality of connections for thewireless device; a variance of quality of connections for the wirelessdevice; a correlation between connections for the wireless device;network conditions impacting connections for the wireless device. 51.The network node of claim 48, wherein the message indicates, in a binarymanner, whether or not the estimated level of the connectivity exceeds arequired level of the connectivity for the service.
 52. The network nodeof claim 48, wherein the message indicates the conditions relating tosaid at least one connection.